Project Data Control Bar

To toggle the display of this control bar:

Your application generates projects that manage both physical files and loaded data objects.

Combining the functions of legacy control bars such as the Project Files and Loaded Data control bars, the Project Data control bar can be used to manage both files and objects using a series of folders and dedicated context-sensitive menus, appropriate to the level of the control bar 'tree' that you are using.

What Do the Different Text Formats Mean?

This control bar lists, amongst other things, a list of loaded 3D overlays. Overlays can be created either automatically by creating data of a new data type (e.g. the first string in a new project session, where no previous string object exists) or manually, say, by duplicating an existing overlay with Copy.

The text format used to describe each overlay provides information on the status of the data object to which it relates.

Bold font	The overlay is used to represent the "current" 3D object for a particular data type. More about current objects...
Italicized font	The overlay represents a 3D object for which there are unsaved 3D changes*

*The important description here is "3D", or something in the underlying data table for the object has changed and hasn't yet been saved. Visual formatting changes are ignored.

You can have any combination of font formatting; a bold, italicized overlay label represents a current data object for which there are unsaved changes.

Application Project Data

Each Studio application contains its own version of a Project Data control bar, using a structure and naming convention that is appropriate to the domain it supports.

Even though the layout and specific functions available will differ between applications, these rules generally apply:

Data within the connected database will be displayed using a tree structure that mimics the organization of the folders on disk that comprise the database. Right-click menus for these folders will be relevant to physical files (for example, loading a file to convert it to an object, viewing file properties, renaming files and so on).
Physical file data that is referenced by a project, but isn't explicitly used in the managed workflow(s) of the target application (such as reference drillholes in Studio Mapper, for example) will be segregated from other database-bound data using an "Other Files" folder.
Data displayed in a 3D window will be split into both unmanaged (reference) and managed data. Managed data is data that is consumed by a function of your product's workflow. This could be channel sample data in Studio Mapper, an ultimate pit shell in Studio NPVS, fixed cross-section design strings in Studio UG and so on).
Plots window data will be isolated in its own folder, with its own menu collection.

The Project Data control bar for each product will contain a mixture of proprietary (often operating domain-specific) functions and functions available elsewhere on the system. For example, many of the data management functions found, say, when right-clicking a database folder will also be available via the Project Files control bar or, if your product has one, a Data ribbon.